Skip to content
This repository was archived by the owner on Oct 22, 2024. It is now read-only.

Update dependency @floating-ui/react to v0.26.24 #4

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft

Update dependency @floating-ui/react to v0.26.24 #4

wants to merge 2 commits into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 6, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@floating-ui/react (source) 0.26.11 -> 0.26.24 age adoption passing confidence

Release Notes

floating-ui/floating-ui (@​floating-ui/react)

v0.26.24

Compare Source

Patch Changes
  • fix(FloatingOverlay): correct multiple locks behavior on iOS
  • fix(FloatingFocusManager): avoid returning focus to nearest tabbable element of the reference if it gets removed when the floating element closes to avoid unwanted focus effects of unrelated elements firing. Tab index context remains preserved if the floating element is portaled.
  • refactor: use React.JSX.Element types. Ensure you've upgraded to the latest @types/react patches (versions since May 6, 2023)
  • fix(FloatingArrow): avoid requiring leading space for manually specified transform style property
  • fix(inner): round maxHeight and apply minItemsVisible only when scrollable
  • Update dependencies: @floating-ui/[email protected], @floating-ui/[email protected]

v0.26.23

Compare Source

Patch Changes
  • feat: add onOpenChange reason string for FloatingFocusManager's closeOnFocusOut handling
  • fix(inner): correctly handle borders
  • fix(FloatingArrow): ignore staticOffset prop if floating element is shifted. Fixes an issue where the arrow could potentially point to nothing if it was shifted enough from its reference element.
  • fix(useListNavigation, Composite): prevent onNavigate from potentially passing in an undefined value instead of null
  • fix(useHover): blockPointerEvents no longer adds pointer-events: none to unintended <body> elements.
  • fix: manage focus on element with floating props spread on it
  • fix(FloatingFocusManager): support keepMounted behavior with disabled prop

v0.26.22

Compare Source

Patch Changes

v0.26.21

Compare Source

Patch Changes

v0.26.20

Compare Source

Patch Changes
  • fix: wrap focus call in act in useFocus tests
  • fix: focus always mounted nested lists with listNavigation
  • fix(FloatingFocusManager): return focus to next tabbable after reference element if removed after floating element opens without other previously focused elements to use
  • fix(useListNavigation): avoid reading ref in render
  • Update dependencies: @floating-ui/[email protected]

v0.26.19

Compare Source

Patch Changes
  • refactor: use scrollX/scrollY instead of deprecated pageXOffset/pageYOffset
  • chore: fix internal dependency versioning
  • Update dependencies: @floating-ui/[email protected]

v0.26.18

Compare Source

Patch Changes
  • fix(useInteractions): split prop getter dependencies so that only the relevant element changes when necessary. Previously reference and floating prop getters had dependencies grouped.
  • fix(useFocus): prevent SyntheticEvent warning on React <17
  • fix(inner): allow to make Derivable
  • fix(FloatingFocusManager): correctly close floating element when tabbing out of a modal combobox reference
  • fix(types): export FloatingPortalProps, CompositeProps, CompositeItemProps
  • chore: fix internal deps
  • fix(FloatingArrow): allow close transitions to play on floating element when grouped in instant phase
  • fix(useHover): prevent unnecessary delayed opens to preserve potential click open events. Fixes an issue when combining useHover and useClick hooks and a click occurred before the floating element could open on hover, it would unexpectedly close on mouseleave despite being triggered by a click.
  • refactor: improve types and internal codebase consistency. All documented types are now exported.
  • Update dependencies: @floating-ui/[email protected]

v0.26.17

Compare Source

Patch Changes
  • fix(FloatingFocusManager): place fallback focus on element with floating props
  • feat(FloatingFocusManager): restoreFocus prop. This enables automatic restoration of focus to the nearest tabbable element if the element that currently has focus inside the floating element is removed from the DOM.
  • fix(useHover): fix restMs options throwing SyntheticEvent warning on React < 17

v0.26.16

Compare Source

Patch Changes
  • fix(useListNavigation): correct scrollIntoView and focus behavior with virtual focus and inner DOM-focused element + FloatingList
  • fix(FloatingPortal): prevent undefined id with unconditional rendering in React <18
  • fix(useListNavigation): prevent selectedIndex changes from stealing focus
  • fix(FloatingDelayGroup): prevent hydration error with Suspense
  • fix(useListNavigation, Composite): correct index calculations for grid navigation with nullish and disabled items when disabledIndices is inferred
  • perf(markOthers): avoid applying attributes to script tags needlessly
  • Update dependencies: @floating-ui/[email protected]

v0.26.15

Compare Source

Patch Changes
  • fix(useTransitionStatus): guard isMounted check and remove unneeded initiated state. Prevents an infinite loop when called in a component with an unstable callback ref.

v0.26.14

Compare Source

Patch Changes
  • feat: add useFloatingRootContext Hook, which enables calling interaction hooks in a component higher in the tree than useFloating is called in. This supports spreading reference props onto an "external" reference element.

v0.26.13

Compare Source

Patch Changes
  • fix(FloatingFocusManager): return focus to reference when applicable even if not focused on open
  • fix(types): simplify React types
  • fix(types): replace React_2 with React in generated .d.ts files
  • fix(types): revert React.JSX.Element back to JSX.Element
  • fix(useHover): restMs + nullish open delay should respect restMs

v0.26.12

Compare Source

Patch Changes
  • fix(useFloating): external element synchronization with domReference and positionReference
  • fix(useFloating): set dataRef openEvent property to undefined on close. Fixes a minor issue when useHover restMs is combined with useClientPoint and focus modality was used before hover modality.
  • fix(useId): avoid import error in new bundlers when using React <18, and also ensure id collisions don't occur when multiple independent versions of Floating UI are used with React <18.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added T-Task Tasks for the team like planning Dependencies Pull requests that update a dependency file labels Sep 6, 2024
@renovate renovate bot force-pushed the renovate/resolutions branch from 8ca016c to 279bc0e Compare September 18, 2024 09:42
@renovate renovate bot changed the title Update dependency @floating-ui/react to v0.26.23 Update dependency @floating-ui/react to v0.26.24 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/resolutions branch from 279bc0e to e3724eb Compare September 19, 2024 19:36
@renovate
Copy link
Contributor Author

renovate bot commented Sep 23, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

Dependencies Pull requests that update a dependency file T-Task Tasks for the team like planning

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@florianduros